Correlating calls after a referral

ABSTRACT

In one embodiment, a network device attaches a header including an identifier for an original call to an outgoing refer message and may also modify a table entry for a consultative call to include the identifier. The network device then monitors incoming invite messages for a header containing the identifier and observes that an incoming invite message containing the header correlates to the original call. When a header is not included, the network device extracts information from the incoming invite messages and compares the extracted information to the modified table entry to correlate one of the incoming invite messages to the original call.

TECHNICAL FIELD

The present disclosure relates generally to the field of networking.

BACKGROUND

Session establishment protocols such as Session Initiation Protocol (SIP) can be used to establish a call between two endpoints. The SIP protocol includes a referral method that allows a transferor to “transfer” a phone call to a transfer target. Under the SIP refer method the transferor establishes a consultative call with the transfer target to determine whether the transfer target will accept a transfer. When the transfer target indicates that the transfer is acceptable, the transferor sends a SIP refer message that includes information about the transfer target to a transferee. The SIP refer message elicits a SIP invite sent from the transferee to the transfer target, which establishes a call between the transferee and the transfer target.

When a Private Branch eXchange (PBX) or other network device for the transferor observes the incoming SIP invite, the PBX is unable to recognize that a new call established with the SIP invite is really a continuation of an original call established with the same remote endpoint. The inability of the PBX to correlate the two calls makes it difficult for a business to track efficiency. For example, a customer service center may need to determine how much time was spent addressing a single request from a customer, which may appear as two requests to the PBX when SIP refer method is used. The disclosure that follows solves these and other problems.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example Private Branch eXchange (PBX) for correlating an original call to a transferred call.

FIG. 2 illustrates an example method for using the PBX illustrated in FIG. 1.

FIG. 3 illustrates another example PBX for correlating an original call to a transferred call.

FIG. 4 illustrates an example method for using the PBX illustrated in FIG. 2.

FIG. 5 illustrates an example method for using a network device that includes the functionality of the PBXs illustrated in FIGS. 1 and 3.

DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

In one embodiment, a network device attaches a header including an identifier for an original call to an outgoing refer message and may also modify a table entry for a consultative call to include the identifier. The network device then monitors incoming invite messages for a header containing the identifier and observes that an incoming invite message containing the header correlates to the original call. When a header is not included, the network device extracts information from the incoming invite messages and compares the extracted information to the modified table entry to correlate one of the incoming invite messages to the original call.

Description

Several preferred examples of the present application will now be described with reference to the accompanying drawings. Various other examples of the invention are also possible and practical. This application may be exemplified in many different forms and should not be construed as being limited to the examples set forth herein.

The figures listed above illustrate preferred examples of the application and the operation of such examples. In the figures, the size of the boxes is not intended to represent the size of the various physical components. Where the same element appears in multiple figures, the same reference numeral is used to denote the element in all of the figures where it appears. When two elements operate differently, different reference numerals are used regardless of whether the two elements are the same class of network device.

Only those parts of the various units are shown and described which are necessary to convey an understanding of the examples to those skilled in the art. Those parts and elements not shown are conventional and known in the art.

FIG. 1 illustrates an example Private Branch eXchange (PBX) for correlating an original call to a transferred call.

The system 100 includes a PBX SA including software 8A for correlating an original call A to a transferred call C and a PBX 6 including software 9 for inserting an identifying header into an invite message. The PBX 5A is a telephone exchange that serves endpoints X and Y, while the PBX 6 serves endpoint Z. In other embodiments, any other network device that exchanges or switches calls for endpoints may instead perform the functions of PBXs 5A and 6.

A customer service agent at the endpoint X located in a customer call center has established a call A with a customer located at the remote endpoint Z. During this original call A, the customer agent at the endpoint X decides to transfer the customer to a different agent at endpoint Y. Accordingly, the agent at endpoint X presses a key or takes some other action that causes the PBX 5A to establish a consultative call B with the endpoint Y.

Once the consultative call B has been established and the agent at endpoint X verifies that the agent at endpoint Y is available to take the call, the agent at endpoint X presses a hook flash key or takes some other action to signal the PBX 5A to transfer the customer to the agent at endpoint Y.

In response to the request from endpoint X, the PBX 5A generates a Session Initiation Protocol (SIP) refer 11 or any other refer message for sending to the endpoint Z. The SIP refer 11 is configured to trigger a SIP invite 12 or other invitation to be sent back, which is used for transferring as described in Request For Comment (RFC) 3515. The RFC 3515 is available on the Internet and herein incorporated by reference in its entirety.

According to the software 8A, the PBX 5A first identifies or assigns a Global Call IDentifier (GCID) 15 or any other call identifier for the original call A. The PBX 5A may identify the GCID 15 by accessing a local table that tracks active calls or by using any other method. Next, the PBX 5A formats a header including this GCID 15 for attaching to the SIP refer 11. The SIP refer 11 is then transferred to the PBX 6.

The PBX 6 receives the SIP refer 11 and generates a SIP invite 12. According to the software 9, the PBX 6 observes whether the SIP refer 11 includes a header having a GCID value. When the PBX 6 observes the GCID 15, the PBX 6 extracts either the header and the GCID 15 or just the GCID 15 from the SIP refer 11 and attaches the same or another header and the GCID 15 to the generated SIP invite 12. The SIP invite 12 is then transferred to the PBX 5A.

The PBX 5A monitors for SIP invites having attached GCID values according to the software 8A. When the PBX 5A observes the SIP invite 12, the PBX 5A causes the call C to be established between the endpoints Y and Z according to the SIP invite 12. According to software 8A, the PBX 5A correlates the newly established call C with the original call A according to the GCID 15 that identifies the call A. The PBX 5A may then update a database to reflect that calls A and C correspond to a same customer issue. This correspondence information may be used by the customer service center to identify how much total time is spent addressing each single customer issue, and to generate other similar statistics.

FIG. 2 illustrates an example method for using the PBX illustrated in FIG. 1.

In block 201, the PBX 5A receives a request to establish a new call, which is sent from an endpoint for a consultative call. The PBX 5A attaches to a refer message a call identifier for an original call to be transferred in block 202. In block 203, the PBX 5A transfers the refer message with the attached call identifier to a remote endpoint for the original call to elicit that remote endpoint to send a call invitation.

In block 204, the PBX 5A monitors for an incoming call invitation that includes the call identifier for the original call. When an incoming call invitation including the call identifier is received, in block 205 the PBX 5A establishes a new call according to the incoming call invitation and correlates that new call to the original call. In block 206, the PBX 5A outputs an indication that the new call and the original call are correlated, which may be used for evaluating performance of a customer service center. The PBX 5A may output the indication by displaying the indication or transferring the indication for display on another device.

FIG. 3 illustrates another example PBX for correlating an original call to a transferred call.

The embodiment show in FIG. 3 functions regardless of whether a network device for the remote endpoint includes the software 9 (FIG. 1) for inserting an identifying header, or even whether the remote endpoint is served by a network device such as PBX 7. In other words, the PBX 7 does not include the software 9 (FIG. 1) and thus does not attach the identifying header to a SIP invite. Therefore, PBX 5B uses a different technique for correlating the original call A to the transferred call C.

In conjunction with establishing the consultative call B, the PBX 5B includes an entry 20 for the call B in an active call table 19. According to correlation software 8B the PBX 5B formats the entry 20 to include the GCID 15 for the original call A. The GCID 15 may be included in the private data space of entry 20 for the call B.

The PBX 5B also sends the SIP refer 21 to elicit the SIP invite 22. The PBX 7 (or another network device such as a phone on endpoint Z) generates the SIP invite 22 according to the SIP refer 21.

Included within the SIP invite 22 is the consult dialog ID 25 for consultative call B. The consult dialog ID 25 is included within the SIP invite 22 according to the SIP refer method, which allows the PBX 5B to identify a consultative call to replace with the new call C requested by the SIP invite 22.

The PBX 5B receives the SIP invite 22, and according to the software 8B, examines the invite 22 to locate the consult dialog ID 25. In other examples, the PBX 5B may examine the invite 22 for other call replacement information that identifies the consultative call B. The PBX 5B compares the consult dialog ID 25 that identifies the consultative call B to the active call table 19 to identify entry 20. The PBX 5B then examines the private data space of the entry 20 to identify the GCID 15 corresponding to call A. Accordingly, the PBX 5B observes that the new call C correlates with the call A. The PBX 5B may store this observation in a local memory or may output this information so that, for example, a call center can recognize that the calls A and C correspond to a single customer issue.

In some embodiments, the functionality of both the software 8A (FIG. 1) and the software 8B (FIG. 3) is included in a single device so that calls can be correlated regardless of pre-knowledge of the capabilities of a remote network device. In other words, a network device may both attach an identifying header and format a table entry and then both examine an invite message for an identifying header and compare call replacement information to the formatted table entry. Such an embodiment is interoperable with a wide variety of remote network devices.

FIG. 4 illustrates an example method for using the PBX illustrated in FIG. 3.

In block 401, the PBX 5B formats entries for consultative calls in an active call table to include call identifiers for original calls to be transferred. In block 402, the PBX 5B sends refer messages to remote endpoints to elicit call invitations.

In block 403, the PBX 5B compares information included in incoming call invitations to the entries to correlate incoming call invitations to the consultative calls. The PBX 5B then correlates new calls that are established according to the incoming call invitations to the original calls using the call identifiers included in the consultative call entries in block 404. The PBX 5B may output the correlations of the new calls to the original calls for statistical use in evaluating the performance of a customer service center in block 405.

FIG. 5 illustrates an example method for using a network device that includes the functionality of the PBXs illustrated in FIGS. 1 and 3.

In block 501, the network device formats entries for consultative calls in an active call table to include call identifiers for original calls to be transferred. In block 502, the network device sends refer messages that include the call identifiers to remote endpoints to elicit call invitations.

In block 503, the network device determines whether an incoming call invitation includes a call identifier. When the call identifier is included in block 504, the network device correlates a new call established using the call invitation to one of the original calls using the call identifier in block 505A. In block 507, the network device may output the correlation of the new call to the original call for statistical use.

When the call identifier is not included in block 504, the network devices compares information included in the incoming call invitation to the entries to correlate the incoming call invitation to one of the consultative calls in block 505B. In block 506, the network device correlates a new call that is established using the call invitation to one of the original calls using the call identifier included in the correlated call entry. The network device may also output the correlation of the new call to the original call for statistical use in block 507.

Several preferred examples have been described above with reference to the accompanying drawings. Various other examples of the invention are also possible and practical. The system may be exemplified in many different forms and should not be construed as being limited to the examples set forth above.

The figures listed above illustrate preferred examples of the application and the operation of such examples. In the figures, the size of the boxes is not intended to represent the size of the various physical components. Where the same element appears in multiple figures, the same reference numeral is used to denote the element in all of the figures where it appears.

Only those parts of the various units are shown and described which are necessary to convey an understanding of the examples to those skilled in the art. Those parts and elements not shown are conventional and known in the art.

The system described above can use dedicated processor systems, micro controllers, programmable logic devices, or microprocessors that perform some or all of the operations. Some of the operations described above may be implemented in software and other operations may be implemented in hardware.

For the sake of convenience, the operations are described as various interconnected functional blocks or distinct software modules. This is not necessary, however, and there may be cases where these functional blocks or modules are equivalently aggregated into a single logic device, program or operation with unclear boundaries. In any event, the functional blocks and software modules or features of the flexible interface can be implemented by themselves, or in combination with other operations in either hardware or software.

Having described and illustrated the principles of the invention in a preferred embodiment thereof, it should be apparent that the invention may be modified in arrangement and detail without departing from such principles. I claim all modifications and variation coming within the spirit and scope of the following claims. 

1. An apparatus, comprising: one or more processors; and a memory coupled to the processors comprising instructions executable by the processors, the processors operable when executing the instructions to: attach a call identifier for a first call to an outgoing refer message, the refer message configured to elicit a remote network device to send a communication identifying a consultative call for replacement; and monitor incoming communications for the call identifier for correlating a new second call with the first call.
 2. The apparatus of claim 1 further comprising: format a locally stored entry for the consultative call with the call identifier for the first call; and identify one of the incoming communications as replacing the consultative call by comparing information included in the incoming communications to the locally stored entry; and output an indication that the new second call established using the identified incoming communication correlates to the first call in response to observing the call identifier for the first call in the locally stored entry.
 3. The apparatus of claim 2 wherein the locally stored entry is located in an active call table and the call identifier is stored in a private data space in the entry for the consultative call.
 4. The apparatus of claim 1 wherein the correlation of the new second call with the first call indicates that both the first call and the new second call that is established using the correlated incoming communication represent a single customer issue.
 5. The apparatus of claim 4 wherein the processors are further operable to output a correlation of the first call with the new second call for use in calculating efficiency trends of a call center that is an endpoint for the first call, the consultative call and the new second call.
 6. The apparatus of claim 1 wherein the outgoing refer message is sent according to a protocol that requires an invitation message from a transferee to execute a call transfer.
 7. The apparatus of claim 6 wherein the protocol is Session Initiation Protocol (SIP).
 8. The apparatus of claim 1 wherein the call identifier is a Global Call IDentifier (GCID).
 9. A system comprising: means for correlating a new call using information included in an incoming invitation message for the new call with an original call; and means for outputting the correlation.
 10. The system of claim 9 wherein the new call is correlated to the original call by comparing information included in the incoming invitation with an entry for a consultative call that is not one of the new call or the original call.
 11. The system of claim 10 wherein a call identifier stored in the entry for the consultative call identifies the original call.
 12. The system of claim 9 wherein the new call is correlated to the original call by observing a call identifier included in the incoming invitation message, the call identifier corresponding to the original call.
 13. The system of claim 12 further comprising means for including the call identifier in an outgoing refer message that elicits the incoming invitation message.
 14. The system of claim 9 wherein the new call is established using Session Initiation Protocol (SIP) and wherein the call identifier is a Global Call IDentifier (GCID).
 15. A method comprising: establishing consultative calls after requests are received for transferring original calls; formatting call entries for the consultative calls with identifiers for the original calls; monitoring incoming messages for information identifying the consultative calls; comparing the information to the call entries to correlate one of the incoming messages with a respective one of the call entries; and outputting an indication that a new call established according to the correlated incoming message is a transfer of the original call identified by the identifier included in the respect call entry
 16. The method of claim 15 wherein the identifiers are Global Call IDentifiers (GCIDs) stored in private data spaces of the call entries.
 17. The method of claim 16 wherein the call entries are stored in a database that includes other entries for other types of active calls.
 18. The method of claim 15 further comprising: generating a refer message that requests the correlated incoming message; and formatting the refer message with a header that includes one of the original call identifiers before transferring the formatted refer message.
 19. The method of claim 18 further comprising: receiving the formatted refer message at an endpoint that is remote from a generation source of the refer message; generating the requested message in response to receiving the formatted refer message; and formatting the requested message with the call identifier included in the received formatted refer message before transferring the requested message.
 20. The method of claim 18 wherein the transferred refer message is a Session Initiation Protocol (SIP) refer having a header including a Global Call IDentifier (GCID).
 21. The method of claim 19 wherein the requested incoming message is a SIP invite having a header including a GCID. 